Reject ARM64EC Windows runtime DLLs#595
Conversation
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 11 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughAdds ARM64EC detection to Windows runtime DLL staging, a new ChangesARM64EC Filtering for Windows Runtime DLLs
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Deploying maple with
|
| Latest commit: |
a7583d5
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://5f1f68ad.maple-ca8.pages.dev |
| Branch Preview URL: | https://fix-windows-vc-runtime-arch.maple-ca8.pages.dev |
69bde5a to
08bde73
Compare
08bde73 to
22a49f8
Compare
22a49f8 to
a7583d5
Compare
Summary
AMD64in the PE Machine fieldInvestigation
Issue #594 reports an Intel x64 launch crash in
VCRUNTIME140_1.dllwithc000001d. The v3.1.2 installer payload is x64 overall, but the bundledVCRUNTIME140_1.dllcontains an ARM64EC PDB marker:binaries\\arm64ret\\bin\\arm64ec\\vcruntime140_1.arm64.pdbThe other VC runtime DLLs are native AMD64. ARM64EC can pass a plain AMD64 PE Machine check, so the old staging script could select the wrong redist payload deterministically.
Verification
nix develop .#ci -c python3 -m py_compile scripts/ci/canonical-windows-nsis-payload-hash.pybash -n scripts/ci/verify-release-artifacts.shgit diff --checknix develop .#ci -c python3 scripts/ci/canonical-windows-nsis-payload-hash.py --verify-runtime-dlls /tmp/maple-win-issue-594/Maple_3.1.2_x64-setup.exe Maple_3.1.2_x64-setup.exefails on published v3.1.2 as expected:VCRUNTIME140_1.dllis ARM64ECnix develop .#ci -c ./scripts/ci/verify-release-artifacts.sh /tmp/maple-win-issue-594 windowsfails on published v3.1.2 as expected before accepting the bad payloadnix develop .#ci -c git commit ...: Prettier check, frontend build, Bun testsFixes #594
Summary by CodeRabbit